bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Tue, 31 May 2022 12:08:49 +0000 (13:08 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Tue, 31 May 2022 12:08:49 +0000 (13:08 +0100)
commitd64e2ff2c0a70794940c329ffceda1432e6e5deb
tree05c0689a3b83dca5a2d025a8d44789e295d15e90
parent7b58bb8fc9cb57827884e4e371f1348e0e448ad0
bootstrap-fix-include-next

When doing a bootstrap, we use a newly built clang.
When this one is used, if already installed on the system,
we have clang header in two places:
llvm-toolchain-7-7/build-llvm/lib/clang/7.0.0/include/inttypes.h
and
/usr/include/clang/7.0.0/include/inttypes.h

Because clang expects only one of his headers to be available, it uses
include_next to get the glibc (libc6-dev package) header.

However, in the previous example, because we have inttypes.h twice in the
include search path, clang's header will call itself without any effect.
Therefore, it will do include_next until the define from the libc is existing (ex: _INTTYPES_H)

Gbp-Pq: Name bootstrap-fix-include-next.diff
clang/lib/Headers/inttypes.h
clang/lib/Headers/limits.h